[8.19] (backport #8083) [Integration Testing] Allow tests to declare themselves as needing a FIPS environment #8095
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mergify
bot
requested review from
blakerouse and
kaanyalti
and removed request for
a team
github-actions
bot
added
Team:Elastic-Agent-Control-Plane
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
|
ycombinator
approved these changes
May 7, 2025
|
This pull request has not been merged yet. Could you please review and merge it @ycombinator? 🙏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR allows integration tests to declare that they should be run in a FIPS-configured environment, e.g. a Linux VM with OpenSSL configured with the FIPS provider.
Further, the Buildkite pipeline for running integration tests is updated with a new group for running these FIPS integration tests. Note the
FIXMEs and commented out sections of the Buildkite pipeline in this PR; they will need to be addressed when a FIPS-configured VM image and an FRH ECH environment are available.Why is it important?
To allow FIPS-related integration tests to declare themselves as needing a FIPS environment, so they can be run in a FIPS-configured environment against an FRH ECH environment.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksI have added an entry in./changelog/fragmentsusing the changelog toolI have added an integration test or an E2E testDisruptive User Impact
None; this PR enhances the integration testing framework.
This is an automatic backport of pull request #8083 done by [Mergify](https://mergify.com).